NTISthis.com

Evidence Guide: ICTSAS505 - Review and update disaster recovery and contingency plans

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTSAS505 - Review and update disaster recovery and contingency plans

What evidence can you provide to prove your understanding of each of the following citeria?

Evaluate impact of system on business continuity

  1. Identify business critical functions and the security environment from documentation and from discussion with business area and project team
  2. Identify critical data and software from documentation
  3. Assess potential impact of business risk and threats on ICT systems
  4. Identify and evaluate statutory requirements, commercial requirements and contingency possibilities according to specifications and cost constraints
Identify business critical functions and the security environment from documentation and from discussion with business area and project team

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify critical data and software from documentation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assess potential impact of business risk and threats on ICT systems

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify and evaluate statutory requirements, commercial requirements and contingency possibilities according to specifications and cost constraints

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate threats to system

  1. Identify threats to the system, considering security analysis and internal and external business environment
  2. Evaluate risk minimisation alternatives against specifications and cost constraints
Identify threats to the system, considering security analysis and internal and external business environment

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate risk minimisation alternatives against specifications and cost constraints

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Formulate prevention and recovery strategy

  1. Evaluate prevention and recovery options to support critical business functions against business specifications and cost constraints
  2. Review current operational procedures to ensure adequate risk safeguards and contingency plans are in place
  3. Submit disaster recovery and prevention strategy to appropriate person for approval
Evaluate prevention and recovery options to support critical business functions against business specifications and cost constraints

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review current operational procedures to ensure adequate risk safeguards and contingency plans are in place

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Submit disaster recovery and prevention strategy to appropriate person for approval

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop disaster recovery plan to support strategy

  1. Identify and document resources required for disaster recovery according to specifications and cost constraints
  2. Identify and document processes required for disaster strategy according to project standards
  3. Identify cut-over criteria before initiating disaster plan
  4. Document disaster recovery plan and submit to appropriate person for review and sign-off
Identify and document resources required for disaster recovery according to specifications and cost constraints

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify and document processes required for disaster strategy according to project standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify cut-over criteria before initiating disaster plan

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document disaster recovery plan and submit to appropriate person for review and sign-off

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Evaluate impact of system on business continuity

1.1 Identify business critical functions and the security environment from documentation and from discussion with business area and project team

1.2 Identify critical data and software from documentation

1.3 Assess potential impact of business risk and threats on ICT systems

1.4 Identify and evaluate statutory requirements, commercial requirements and contingency possibilities according to specifications and cost constraints

2. Evaluate threats to system

2.1 Identify threats to the system, considering security analysis and internal and external business environment

2.2 Evaluate risk minimisation alternatives against specifications and cost constraints

3. Formulate prevention and recovery strategy

3.1 Evaluate prevention and recovery options to support critical business functions against business specifications and cost constraints

3.2 Review current operational procedures to ensure adequate risk safeguards and contingency plans are in place

3.3 Submit disaster recovery and prevention strategy to appropriate person for approval

4. Develop disaster recovery plan to support strategy

4.1 Identify and document resources required for disaster recovery according to specifications and cost constraints

4.2 Identify and document processes required for disaster strategy according to project standards

4.3 Identify cut-over criteria before initiating disaster plan

4.4 Document disaster recovery plan and submit to appropriate person for review and sign-off

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Evaluate impact of system on business continuity

1.1 Identify business critical functions and the security environment from documentation and from discussion with business area and project team

1.2 Identify critical data and software from documentation

1.3 Assess potential impact of business risk and threats on ICT systems

1.4 Identify and evaluate statutory requirements, commercial requirements and contingency possibilities according to specifications and cost constraints

2. Evaluate threats to system

2.1 Identify threats to the system, considering security analysis and internal and external business environment

2.2 Evaluate risk minimisation alternatives against specifications and cost constraints

3. Formulate prevention and recovery strategy

3.1 Evaluate prevention and recovery options to support critical business functions against business specifications and cost constraints

3.2 Review current operational procedures to ensure adequate risk safeguards and contingency plans are in place

3.3 Submit disaster recovery and prevention strategy to appropriate person for approval

4. Develop disaster recovery plan to support strategy

4.1 Identify and document resources required for disaster recovery according to specifications and cost constraints

4.2 Identify and document processes required for disaster strategy according to project standards

4.3 Identify cut-over criteria before initiating disaster plan

4.4 Document disaster recovery plan and submit to appropriate person for review and sign-off

Evidence of the ability to:

develop a contingency plan that identifies threats and minimises down time for business critical functions

develop clear and specific directions on how to handle serious down time

coordinate, plan and articulate flexible logistics requirements.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

compare and contrast backup methodologies

explain the business planning process relevant to the development of information and communication technology (ICT) business solutions

analyse the client business domain

evaluate disaster recovery plan strategies and components, including:

physical security

system failure, accident or sabotage (hackers)

denial of service

virus attack

cyber attack

telecommunications failure

contingency arrangements

interpret and analyse key workplace health and safety, legislative and organisational requirements relevant to the task

evaluate the organisation’s current systems functionality and systems engineering.